releasing memory in apply diff #4193
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related GitHub Issue
Closes: nothing, simply a memory optimization to avoid greyscreens.
Description
This PR addresses a potential memory leak in the applyDiffTool by explicitly releasing the
originalContentbuffer after it's used for diff application.Type of Change
Important
Optimize memory usage in
applyDiffToolby releasingoriginalContentafter use.applyDiffToolfunction inapplyDiffTool.ts, releaseoriginalContentvariable by setting it tonullafter diff application to prevent memory leaks.This description was created by
for 95c005b. You can customize this summary. It will automatically update as commits are pushed.